Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java: remove explicit jdk setup #917

Closed
wants to merge 1 commit into from
Closed

java: remove explicit jdk setup #917

wants to merge 1 commit into from

Conversation

junr03
Copy link
Member

@junr03 junr03 commented Jun 17, 2020

Signed-off-by: Jose Nino jnino@lyft.com

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md

Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

Signed-off-by: Jose Nino <jnino@lyft.com>
@junr03
Copy link
Member Author

junr03 commented Jun 18, 2020

@buildbreaker I noticed you added jdk setup in #877 for javadocs, but I think that might be causing issues now against the example apps: https://github.com/lyft/envoy-mobile/runs/782461117#step:8:70 and what is installed in the github actions mac ci agents

@buildbreaker
Copy link

@junr03 We'll likely get another issue but this looks like a proguard issue with android-30?

A similar issue a few years back: bazelbuild/bazel#3777

@buildbreaker
Copy link

buildbreaker commented Jun 18, 2020

Likely cause: actions/runner-images#1030?

Just to give a little more color onto the jdk specification. macos-latest in github actions uses the latest jdk (14?). After some version (it's like jdk 12 or something), they stopped shipping some tools.jar which javadoc generation jar relies on

@buildbreaker
Copy link

Let's try: #918?

@junr03 junr03 closed this Jun 23, 2020
@junr03 junr03 deleted the jdk-test branch June 23, 2020 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants